Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add internalClusterTest to check task #53444

Merged
merged 4 commits into from
Mar 17, 2020
Merged

Conversation

rjernst
Copy link
Member

@rjernst rjernst commented Mar 12, 2020

This commit adds internalClusterTest in xpack core to run as part of
check. This was accidentally removed in a refactoring. Other xpack
modules already do this, but core was left out. This commit also mutes 2
tests that currently fail.

closes #53407

This commit adds internalClusterTest in xpack core to run as part of
check. This was accidentally removed in a refactoring. Other xpack
modules already do this, but core was left out. This commit also mutes 2
tests that currently fail.

closes elastic#53407
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@@ -53,6 +54,7 @@
import static org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertHitCount;

@ESIntegTestCase.ClusterScope(numDataNodes = 0)
@LuceneTestCase.AwaitsFix(bugUrl = "https://github.com/elastic/elasticsearch/issues/53442")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this test has been fixed. The AwaitsFix can be removed here

Copy link
Contributor

@mark-vieira mark-vieira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Although I'm wondering if we should do something more generic like check.dependsOn tasks.withType(Test) in BuildPlugin. We'd have to make some exceptions for things like packaging tests and BWC. Perhaps somethign in the testing conventions plugin to freak out if there's a Test task that no other task depends on? That might be difficult to do though in a way that doesn't completely destroy lazy task configuration.

@rjernst
Copy link
Member Author

rjernst commented Mar 17, 2020

I agree we should look at other ways to make this more robust, but I think that is beyond the scope of this PR, which is simply to re-enable these tests as they are now. Let's follow up within the build area to see how we can better model these tests in gradle.

@rjernst rjernst merged commit 3608be6 into elastic:master Mar 17, 2020
@rjernst rjernst deleted the ic_test_check branch March 17, 2020 01:54
rjernst added a commit that referenced this pull request Mar 17, 2020
This commit adds internalClusterTest in xpack core to run as part of
check. This was accidentally removed in a refactoring. Other xpack
modules already do this, but core was left out. This commit also mutes 2
tests that currently fail.

closes #53407
rjernst added a commit that referenced this pull request Mar 17, 2020
This commit adds internalClusterTest in xpack core to run as part of
check. This was accidentally removed in a refactoring. Other xpack
modules already do this, but core was left out. This commit also mutes 2
tests that currently fail.

closes #53407
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team v7.6.2 v7.7.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

*IT tests in x-pack/plugin/core silently ignored?
5 participants